Business Analyst Community & Resources | Modern Analyst

What is Thinking Outside the Box?

Adrian M. — Sun, 23 Nov 2025 22:30:00 GMT

Thinking outside the box is the ability to move beyond obvious or conventional solutions and reframe a problem so you can discover better options—while still staying grounded in business goals, constraints, and risks.

For a business analyst, that usually shows up in a few ways:

Challenging assumptions - Instead of accepting “this is how the process works,” you question why it’s done that way, what constraints are real vs. historical, and whether the original problem is even defined correctly.

Reframing the problem - You don’t just ask, “How do we build what the stakeholder requested?” You also ask, “What outcome are they really trying to achieve?” and “Is there a completely different way to achieve it?”

Looking across domains - You combine ideas from process improvement, UX, data, automation, and even policy changes. Sometimes the most effective solution is not a new system feature but a workflow change, a template, or a different handoff between teams.

Generating multiple, feasible options - Thinking outside the box isn’t random creativity; it’s structured. You use tools like root cause analysis, journey mapping, and “what if” scenarios to propose several viable alternatives, then help stakeholders evaluate them against value, cost, and risk.

For example, if sales asks for “a new weekly report” because they can’t track performance, an inside-the-box response is to design that report. Thinking outside the box might lead you to propose real-time dashboards, automated alerts when KPIs slip, and simplified data capture—addressing the visibility issue more effectively than the original request.

So, in summary, thinking outside the box as a BA is structured, outcome-focused creativity: challenging assumptions, reframing the problem, and exploring innovative yet practical options that deliver more value than the default solution.

What is Wardley Mapping?

Adrian M. — Tue, 10 Jun 2025 04:01:00 GMT

Wardley Mapping is a strategic visualization technique created by Simon Wardley. It plots all the components required to satisfy a single user need on a two-dimensional chart:

Vertical axis – Value Chain: visibility to the end user, from customer-facing features at the top to commodity infrastructure at the bottom.
Horizontal axis – Evolution: maturity of each component, moving left-to-right through Genesis → Custom-built → Product/Rental → Commodity/Utility.

Core Elements of Wardley Mapping

User Need – the anchor at the top.
Components – activities, data, practices, or technologies enabling that need.
Movement – arrows indicating strategic plays (e.g., open-source, outsource, retire).
Patterns & Doctrine – Wardley’s heuristics for testing the map’s logic.

Typical Wardley Mapping Steps

Define scope and user need (e.g., “borrower receives loan approval”).
Inventory components via interviews, logs, and architecture diagrams.
Draw the value chain top-to-bottom, linking dependencies.
Place components on the evolution axis using signals such as ubiquity and market change rate.
Stress-test with patterns (commoditization, inertia) and doctrine (“focus on user”).
Derive options – outsource commodities, invest in differentiating genesis items, standardize products.
Translate insights into backlog items, sourcing decisions, and roadmap themes.

Why It Matters

Wardley Mapping converts abstract strategy into a single, shared picture that exposes blind spots and looming commoditization. By revealing where each activity sits in both the customer’s line of sight and the market’s evolutionary curve, it makes build-versus-buy, cloud migration, and investment choices almost self-evident. The map fosters rapid consensus across business, technology, and finance because stakeholders debate evidence they can all see rather than hidden assumptions. As the environment shifts, the map also highlights areas vulnerable to disruption, enabling pre-emptive moves and continuous alignment with user value—exactly the kind of situational awareness a business analyst needs to keep initiatives on target.

Wardley Mapping gives business analysts a crisp, evidence-backed lens for prioritization and strategic guidance, letting the landscape—rather than hierarchy or opinion—dictate where time, talent, and budget should go.

Example

In an online mortgage platform, the borrower UI may fall under Product, the proprietary underwriting algorithm under Custom-built, and cloud hosting under commoditized Utility. The map immediately suggests outsourcing hosting, protecting and enhancing the algorithm, and leveraging ready-made UI frameworks to accelerate delivery.

What is Decomposition?

Adrian M. — Wed, 11 Oct 2023 02:30:00 GMT

Decomposition is the process of breaking down complex systems, problems, or tasks into smaller, more manageable and understandable components or sub-parts. It is often used in various fields, such as software development, project management, and business analysis, to simplify complex problems and facilitate analysis, understanding, and problem-solving by addressing individual elements separately.

In requirements management, decomposition is the process of breaking down high-level or complex requirements into smaller, more detailed and manageable sub-requirements. This approach allows for a more in-depth understanding of what the system or product needs to accomplish and helps in creating a structured and organized set of requirements. It is often helpful to develop visual models which depict the hierarchical structure of the requirements. High-level or top-level requirements are subdivided into lower-level or more granular requirements. This hierarchy provides clarity and helps stakeholders understand the relationships between different requirements.

In systems development, decomposition refers to the process of breaking down a complex system or project into smaller, more manageable components, modules, or tasks. This approach is often used in software development, but it can apply to various systems development methodologies, including the systems engineering process.

In business analysis, decomposition refers to the process of breaking down complex business processes, systems, or problems into smaller, more understandable and manageable chunks. This technique is used to analyze, understand, and document the various aspects of a business or project, helping business analysts and stakeholders gain insights into the structure, functions, and interactions within an organization.

Here are some examples where a business analyst can use decomposition to their advantage:

Process Analysis - decomposition can be used to break down complex business processes into their individual steps or activities. This helps identify bottlenecks, inefficiencies, and areas for improvement.

Requirements Analysis - high-level business requirements are often decomposed into more detailed and specific functional and non-functional requirements. This process helps clarify what the business or project needs to achieve.

Data Modeling and Data Analysis - decomposition is used to break down complex data structures into their constituent data elements or attributes. This helps in the creation of data models and database schemas.

System and Component Analysis - in software or IT-related projects, decomposition can be applied to understand the various components, modules, and interfaces within a system. It helps in designing and building systems with a clear understanding of how the various pieces work together.

What is Soft Systems Methodology (SSM)?

Adrian M. — Tue, 15 Aug 2023 03:50:00 GMT

Soft systems methodology (SSM) is a structured approach to thinking, problem solving, and systems analysis that was developed to address very complex or soft (ill-defined) problems where there are divergent views about the very definition of the problem to be solved.

In the worlds of Peter Checkland, the creator of the soft systems methodology:

“Soft Systems Methodology (SSM) is a cyclic learning system which uses models of human activity to explore with the actors in the real world problem situation, their perceptions of that situation and their readiness to decide upon purposeful action which accommodates different actor’s perceptions, judgments and values.”

SSM technique works by acknowledging that complex real-world problems cannot be easily defined in terms of clear or measurable dimensions (hard definitions). A variety of perspectives, conflicting goals, divergent ideas, and subjective interpretations require a “soft”-er approach to the messy problem.

Some of the key principles and of Soft Systems Methodology (SSM) include:

Human-Centric Approach - SSM is designed to handle problems that involve human interactions, social structures, and subjective perceptions by emphasizing understanding people's viewpoints, beliefs, and concerns.
Iterative Process - SSM encourages an iterative approach, where models and solutions are refined based on feedback and ongoing learning.
Problem Structuring - SSM helps structure complex problems in a way that makes them more manageable by enabling stakeholders to identify the root causes of issues and potential areas for intervention.
Holistic Perspective - SSM considers a variety of viewpoints and takes a holistic view of the problem situation by recognizing that a problem cannot be fully understood by only looking at the individual parts..
Collaborative Approach - SSM involves collaboration among stakeholders with diverse perspectives by encouraging dialogue, shared understanding, and joint problem-solving.

While variations exist in the approach to soft systems management, the following 7 steps are generally considered the foundation of the SSM Process:

SSM Step 1 - Appreciate the problem situation
- Identify the problem situation and the various stakeholder perspectives

SSM Step 2 - Describe the problem
- Create a "Rich Picture" that visually represents the problem context

SSM Step 3 - Formulate root definitions
- Identify the relevant systems of interest within the problem domain.
- Develop a root definition for each system

SSM Step 4 - Build conceptual models
- Develop conceptual models for each system using diagrams
- Illustrate the components, interactions, and processes of each system

SSM Step 5 - Compare models with real world
- Compare the constructed models with the real-world situation
- Identify discrepancies, contradictions, and areas of concern between the models and the reality

SSM Step 6 - Define possible changes
- Identify potential changes that could address the defined discrepancies
- Consider changes that are technically feasible and align with stakeholder interests

SSM Step 7 - Recommend actions
- Develop action plans for implementing the selected changes
- Monitor the implementation process and learn from the outcomes to refine the the solution

Let’s finish the overview of the soft systems methodology by focusing introducing three key concepts:

Rich Pictures - Visual presentations of a complex system highlighting the key considerations of the problem to be solved, showing the complexity and various perspectives of the situation. The “rich picture” can include all the necessary elements of the complex domain including: stakeholders, activities, issues, relationships, context, etc.

Root Definitions - In SSM, the root definition is a concise description of the system which names the system in a structured way.

CATWOE - Is a set of concerns which when used properly help define the problem domain and to express the “root definition” in terms of: Customers, Actors, Transformation Process, Worldview, Owner, and Environment Constraints. The “root definition” can be express as follows: “A system owned by [OWNERS], where [ACTORS] perform [TRANSFORMATION] on behalf of [CUSTOMERS] because [WORLDVIEW], but limited by [ENVIRONMENT].”

What is AI as a Service (AIaaS)?

Adrian M. — Sun, 09 Apr 2023 21:47:00 GMT

AI as a Service (AIaaS) refers to the delivery of artificial intelligence (AI) services and technologies over the internet as a cloud-based platform. AIaaS vendors typically offer a range of pre-built interfaces, machine learning models, and other tools that developers can use to build AI-powered applications.

Businesses can leverage AIaaS to access AI technologies without having to invest in expensive hardware, software, and technical expertise.

AIaaS can help businesses reduce costs, improve efficiency, enhance customer experience, and make better decisions.

Examples of AIaaS offerings include natural language processing (NLP), computer vision, predictive analytics, and speech recognition.

AIaaS is a cost-effective and scalable way for businesses to incorporate AI technologies into their operations and services.

AIaaS services can be used to build a variety of applications such as chatbots, virtual assistants, recommendation engines, and fraud detection systems.

AIaaS offers a way for businesses to incorporate AI technologies into their operations and services, without having to develop and maintain their own AI infrastructure.

There are many types of AIaaS offerings including:

Application Programming Interface (APIs)
Machine Learning (ML) Frameworks
No-Code or Low-Code ML Services
Chatbots & digital assistance
Fully managed machine learning services

Now, why should a business analyst care about AIaaS? Well, as a business analyst, your job is to analyze the needs and requirements of your organization, identify areas for improvement, and recommend solutions. AIaaS can help you do that by providing access to AI technologies that can automate processes, improve decision-making, and enhance customer experience.

By leveraging AIaaS, you can help your organization:

Reduce costs - With AIaaS, businesses can leverage the power of AI without having to invest in expensive hardware, software, and technical expertise. This can help reduce costs and improve the bottom line.

Improve efficiency - AI can automate tasks and processes, freeing up employees to focus on more complex tasks that require human expertise. This can help improve overall efficiency and productivity.

Enhance customer experience - AI technologies such as chatbots, recommendation engines, and personalized content can help businesses deliver a more personalized and seamless customer experience.

Make better decisions - AI-powered analytics can help businesses make better decisions by providing insights and recommendations based on data analysis.

How can a GPT help the business/systems analyst?

Adrian M. — Sun, 09 Apr 2023 18:30:00 GMT

First, let’s define GPT. GPT stands for “Generative Pre-trained Transformer” and it refers to a type of deep learning artificial intelligence model that is trained on large amounts of text data to generate human-like text. A business/systems analyst could use generative pre-trained models, such as ChatGPT, in several ways to improve their efficiency and productivity...

What is XD?

Adrian M. — Sat, 12 Nov 2022 21:43:00 GMT

While XD is an acronym for a number of terms, in the world of the analyst XD stands for eXperience Design.

Experience Design (XD) is the practice (or discipline) of focusing on the people’s experience when using a given product or service. The XD practitioner approaches the design by considering the intended customer’s:

needs
feelings
emotions
mindset
expertise

Experience Design (XD) considers the impact of the prescribed interaction on the customer’s satisfaction in a variety of ways:

What are the customer’s expectations in terms of speed of the software?

Is the product usable by people with disabilities (hearing impaired, visually impaired, mobility impaired,d etc.)?

What could frustrate the customer as they use our product?

What assumptions could the customer have prior to using our service?

In order to achieve a positive user experience (UX), the XD team can use a number of different techniques and tools such as:

Persona Definition - identify the types of users the product or service is meant to serve.

User Research - detailed analysis and investigation of the habits, needs, wants, and peculiarities of the intended audience.

Focus Groups - talk and interact with the future users of the product.

Interface Definition - clearly and intentionally defining how the prospective customer will interface with your product or your service.

Prototyping - creating a scaled down version of the final product but more than just a conceptual design, allowing prospective customers to try your idea.

Beta Testing - enable a sample of the intended audience to try out your product and provide feedback - watching the customer use your product is also very valuable.

What else does XD stand for besides eXperience Design?

XD = Adobe XD

XD = eXtreme Design

XD = eXtreme Digital

XD = eX-Dividend

XD = Laughing face emoji

What are some of the questions a business analyst should ask to determine the most appropriate way to Measure Solution Performance (a key task in the BABOK Solution Evaluation knowledge area)?

Chris Adams — Tue, 01 Feb 2022 21:23:00 GMT

The following are the types of questions to ask when determining how to measure solution performance. These will provide the business analyst guidance on how to support Solution Evaluation.

What are the Business Analysis Knowledge Areas?

Chris Adams — Tue, 07 Dec 2021 20:56:00 GMT

This question is an easy way for a hiring manager or an HR professional to screen out candidates who may have under-invested in their career or may lack understanding of the business analysis profession. The 6 Knowledge Areas are:

Elicitation & Collaboration
Requirements Analysis & Design Definition
Solution Evaluation
Requirements Life Cycle Management
Business Analysis Planning & Monitoring
Strategy Analysis

Describe in general terms how a Business Analyst supports Solution Evaluation.

Chris Adams — Mon, 08 Nov 2021 16:23:00 GMT

The interviewee should be familiar with how the Business Analyst supports Solution Evaluation. The IIBA BABOK Solution Evaluation knowledge area includes a number of tasks to evaluate a solution but is not the only source. The interviewee should demonstrate a good understanding of how the BA participates in Solution evaluation.

Measure Solution Performance, Analyze Performance Measures, Assess Solution Limitations, Assess Enterprise Limitations, Recommend Actions to Increase Solution Value

Is it a Defect or is it an Enhancement? How to manage the disagreements.

Chris Adams — Tue, 06 Apr 2021 19:25:00 GMT

“It is a defect, or an enhancement” is one of those arguments in software development that never seems to satisfy anyone when someone makes a decision. I’ve gone so far as to say it is a defectment. It’s really a combination of both. However, that doesn’t necessarily answer the question - nor provide guidance to a resolution.

What is your "Definition of Done"?

Chris Adams — Wed, 02 Dec 2020 20:30:00 GMT

The Scrum Guide's definition of Done (DoD) is shared and agreed upon within the Scrum team. An item is "Done" when a backlog item/increment is potentially shippable. Where, at the end of a Sprint, you must have something complete and ready to ship, but shipping is not required.

What are the four fundamental methods of requirement verification?

Chris Adams — Sun, 08 Sep 2019 16:00:00 GMT

The four fundamental methods of verification are Inspection, Demonstration, Test, and Analysis. The four methods are somewhat hierarchical in nature, as each verifies requirements of a product or system with increasing rigor.

What information should be included in a feasibility assessment?

Chris Adams — Fri, 07 Sep 2018 16:50:00 GMT

The purpose of a feasibility assessment is to evaluate whether a proposed solution can be expected to provide the desired business benefits, and to identify any barriers or risks that could potentially impact solution viability, value or benefit. The feasibility assessment is typically conducted at a point in the project where alternative solutions are being compared prior to selecting a single go-forward solution or approach. If there is only one potential solution or approach being considered, it is still beneficial to conduct a feasibility assessment in order to verify the viability of that solution before investing fully.

How is the Solution Assessment and Validation knowledge area of the BABOK v2.0 defined?

Chris Adams — Sat, 05 Jun 2010 22:15:00 GMT

The purpose of the Solution Assessment and Validation knowledge area of BABOK is to determine how closely a solution meets the original stakeholder and solution requirements as well as describe the activities that the business analyst should complete to ensure the successful implementation of solution. These activities and tasks can be performed by the business analyst regardless of the type of solution being implemented including a new or revised business process, organizational structure, outsourcing agreement, software application, etc.

The tasks involved in solution assessment and validation can be performed on a single solution or be used to compare several solutions for the one which will best satisfy stakeholder and solution requirements while minimize implementation risk. Additionally, the business analyst will determine which solution, if any, provides enough business value to justify its implementation.

The tasks involved in the Solution Assessment and Validation knowledge area include:

Assess Proposed Solution
Allocate Requirements
Assess Organizational Readiness
Define Transition Requirements
Validate Solution
Evaluate Solution Performance

What are the characteristics of a good requirement?

Chris Adams — Sat, 07 Nov 2009 20:11:00 GMT

While different organizations and authors may describe a slightly modified list, the following characteristics are generally accepted as those defining a good requirement.

Cohesive, Complete, Consistent, Modifiable, Correct, Observable, Feasible, Unambiguous, Verifiable

What is the role of the business systems analyst in testing?

manan — Fri, 29 Feb 2008 20:45:00 GMT

The business systems analyst is often responsible for ensuring that the business requirements are satisfied by the final system implementation. This is called requirements validation.

Depending on the organization, a business analyst can be involved in a variety of testing activities:

One requirements validation technique used by business analysts and systems analysts is the creation of test cases to ensure the final implementation supports the system requirements. Creation of test cases prior to design and implementation often discover problems long before they occur in system development. Test cases could be created by the business analyst or the business analyst could be a reviewer or approver of the test cases created by the testing team.

Business Analysts who are part of a SCRUM team may either help the testers on the team or may actually be responsible for unit testing the code created by the team in cases when there are no dedicated testers.

It is also not uncommon, for business analysts to assist with end-to-end integrated testing performed by the technology team or assisting with User Acceptance Testing (UAT) performed by the business team or business users.